- Obtain the image file that will be used in the transaction.
The graphic file should be stored in a location available to the author. Consideration could be given to creating a location for storing base64 images as txt files that can be copied into the transaction.
- Open a website like http://www.motobit.com/util/base64-decoder-encoder.asp or a tool that will take a graphic image and convert it to base64 encoded.
- Make certain that the field where you will be placing the base64 encoded image is already in the transaction file to ensure that it is correctly placed in the transaction hierarchy.
- In an XML editing tool like XMLSpy, open the transaction as an xml file. Navigate to the field where the image will be stored. This field name will be used when authoring the REQ file to “call” the image into the document.
Updating the transaction in the Requirements Editor tool will not work. The transaction must be updated outside of Requirements Editor. Once updated to include the base64 encoded image, the transaction can be used with Requirements Editor.
- Copy all of the base64 encoded content into the field in the transaction. Save the updated transaction.
A Loan Origination Service could use this transaction image as a way to include the appropriate Loan Officer’s electronic signature in documents they generate. This could be done by using a field called LoanOfficerSignature and trigger the appropriate base64 encoded signature to be included in the transaction.